Secure Internal Control for Encrypting Video Data

ABSTRACT

In one aspect, a video processing device includes a processor and a transmitter, for example implemented as separate integrated circuits on a printed circuit board. Pins on the processor are coupled to pins on the transmitter via a data channel, for example conductive leads on the printed circuit board. Video data is transmitted from the processor to the transmitter via this data channel, which is high speed enough to accommodate video data. The transmitter also includes an encryption engine used to encrypt the video data. Encryption control data, which determines the encryption to be applied, is transmitted from the processor to the transmitter over the same data channel as the video data. This is more secure than transmitting the encryption control data over a slower separate data channel, because the high speed video channel is harder to tamper with.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application Ser. No. 62/061,630, “Secure Control Communication between an Application Processor and a Transmitter,” filed Oct. 8, 2014. The subject matter of all of the foregoing is incorporated herein by reference in their entirety.

BACKGROUND

1. Field of the Disclosure

This disclosure relates generally to video data processing and transmission, and more particularly, to the encryption of video data and transmission of encrypted video data.

2. Description of the Related Art

Consumer video processing devices, e.g., smart phones, can transmit high-definition video data to a display device for playback, e.g., on an HDTV. In some cases, the video data is required to be encrypted before transmission to the playback device. Somewhere, within the device, the required level of encryption is specified to an encryption engine and then that level of encryption is applied. However, if the internal structure of the device is not secure, the device may be vulnerable to tampering. The encryption level to be applied could be changed without authorization, resulting in transmission of video data that is unencrypted or underencrypted.

Thus, there is a need for a more secure internal control of the encryption function.

SUMMARY

Embodiments of the present disclosure overcome the limitations of the prior art by providing a video processing device, in which encryption control data is provided to the internal encryption engine using the same high speed internal data channel as used to provide the video data.

In one embodiment, a video processing device includes a processor and a transmitter, for example implemented as separate integrated circuits on a printed circuit board. Pins on the processor are coupled to pins on the transmitter via a data channel, for example conductive leads on the printed circuit board. Video data is transmitted from the processor to the transmitter via this data channel, which is high speed enough to accommodate video data. The transmitter also includes an encryption engine used to encrypt the video data. Encryption control data, which determines the encryption to be applied, is transmitted from the processor to the transmitter over the same data channel as the video data. This is more secure than transmitting the encryption control data over a slower separate data channel, because the high speed video channel is harder to tamper with.

Other aspects include components, devices, systems, improvements, methods, processes, applications and other technologies related to the foregoing.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure has other advantages and features which will be more readily apparent from the following detailed description of the disclosure and the appended claims, when taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of a system using some embodiments.

FIG. 2 is a block diagram showing a processor and a transmitter according to another embodiment.

FIG. 3 is a flow diagram illustrating status reporting.

FIG. 4 is a state diagram illustrating locking of encryption level.

FIG. 5 is a block diagram of one example implementation.

FIG. 6 is a block diagram of another example implementation.

The figures depict embodiments of the present disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The figures and the following description relate to preferred embodiments by way of illustration only. It should be noted that from the following discussion, alternative embodiments of the structures and methods disclosed herein will be readily recognized as viable alternatives that may be employed without departing from the principles of what is claimed.

FIG. 1 is a block diagram of a system using some embodiments. A video processing device 110 transmits video data 139 to a sink/external device 150 via an external data channel 138. The video data 139 is supposed to be encrypted by the video processing device 110 before transmission to the sink 150. If the video processing device 110 does not encrypt the video when it is supposed to, the video data 139 may be transmitted without encryption or with inadequate encryption, resulting in adverse consequences. Various embodiments of this disclosure are advantageous to better ensure that the video data 139 is properly encrypted.

The video processing device 110 includes a processor 120 and a transmitter 130, which typically are implemented as separate integrated circuits within device 110. In certain embodiments, the video processing device 110 may be a mobile phone, a tablet, or some other type of hand held smart device. Other examples include various video transmitting devices, such as notebook computer or other personal computer, DVD player, Blu-ray player, AV receiver, game console, etc. The processor 120 communicates to the transmitter 130 via internal data channel 122, which may be metal leads on a printed circuit board connecting corresponding pins on the two integrated circuits 120,130. The interface to data channel 122 on the processor 120 will be referred to as the data transmit interface 121, and the interface on the transmitter 130 will be referred to as the data receive interface 131. Unencrypted video data 123 is transferred from the processor 120 to the transmitter 130 via the internal data channel 122. The internal data channel 122 is capable of supporting high speed video data transmission and is therefore generally less vulnerable to attack than lower speed channels between the processor 120 and transmitter 130. In various embodiments, the internal data channel 122 may be implemented as several lanes and is capable of bandwidths of at least 2 Gbps in the aggregate over all lanes. Using HDMI as an example, HDMI is typically implemented as three lanes. For standard definition (SD), HDMI supports 0.75 Gbps per lane or a total of 2.25 Gbps of video data. For high definition (HD), HDMI supports 1.5G bps per lane or a total of 4.5 Gbps. For 4K definition, HDMI supports 6 Gbps per lane or a total of 18 Gbps.

The transmitter 130 further includes an encryption engine 134 coupled to the data receive interface 131, and a data output interface 136 coupled to the encryption engine 134. The data path for video within the transmitter 130 is the following. Unencrypted video data is received at data receive interface 131, it is encrypted by encryption engine 134, and then encrypted video data is output from data output interface 136. The encryption engine 134 encrypts the unencrypted video data 132 in accordance with encryption control data 124/133.

The encryption control data 124 is provided to the encryption engine 134 for specifying a level of encryption to be applied by the encryption engine 134 to the unencrypted video data 132. In other words, the encryption control data determines the level of encryption to be applied to the unencrypted video data 123. The level of encryption is selected from a predetermined set of possible levels of encryption, including a level of no encryption. In the HDMI/HDCP example, the possible levels of encryption include HDCP 2.2, HDCP 1.4 and no encryption. In one embodiment, the encryption engine 134 may include a register 135 to store the level of encryption to be applied by the encryption engine 134.

The encryption control data 124 is transferred from the processor 120 to the transmitter 130 via the same internal data channel 122 as the unencrypted video 123. In the HDMI example, the encryption control data (and other audio and auxiliary data) can be transmitted during data island periods. In HDMI, a data island period occurs during the horizontal or vertical blanking intervals, i.e., between the periods when the video data are transmitted. The encryption control data 124 typically is much lower bandwidth than the video 123, so transmission of the encryption control data 124 does not require the high speed transmission of the internal data channel 122. However, transmission on a lower speed channel between the two chips 120, 130 makes the encryption more susceptible to interception, spoofing or other tampering. Within the transmitter 130, the encryption control data 133 may be separated from the video 132 and transmitted along a separate channel to the encryption engine 134.

After encryption, the data output interface 136 transmits the encrypted video data 137 to an external data channel 138. The external data channel 138 is coupled to a sink/external device 150, e.g., an HDTV, which decrypts and renders the content of the encrypted video data 139 for display. In various embodiments, the external device 150 may be any external display device suitable for display of the video, e.g., monitor, AV receiver, tablet, etc.

In one embodiment, the data transmitted by the data output interface 136 is high-definition video data and/or in compliance with High-Definition Multimedia Interface (HDMI) or Mobile High-Definition Link (MHL) standards and the encryption engine 134 is a High-bandwidth Digital Content Protection (HDCP) encryption engine. In other embodiments, the data transmitted by the data output interface 136 is in compliance with other specifications such as DisplayPort using HDCP encryption, Miracast (or other WiFi standards) using HDCP encryption, and USB using HDCP encryption. Other types of encryption may also be used.

As an additional function, the device 110 may check if the sink/external device 150 supports a required, minimum level of encryption specified by the encryption control data. If the device 110 determines that the sink/external device 150 does not support the minimum level of encryption, the transmitter 130 may be configured to not transmit data over the external data channel 138.

The video data for the processor 120 may come from many data sources, some of which are shown in FIG. 1. For example, video data 114 may be received from an external video data source (not shown), via a video port 113 to a wired or wireless connection. Alternately, video data 112 may be accessed from a memory or other storage medium 111. The memory 111 may be read-only or be both readable and rewritable. In the embodiment shown in FIG. 1, the memory is part of the video processing device 110. In other embodiments, the memory 111 may be external to the video processing device 110 and/or removable. For example, the memory 111 may be a USB drive or hard disk, or a blue-ray player or any other video player with an optical disc drive or other types of storage.

FIG. 2 is a block diagram showing a processor and a transmitter according to another embodiment of the disclosure. This embodiment further includes a side channel 240 between the processor 120 and the transmitter 130 for the transmission of control signals 241 between the two. The interface on the transmitter 130 will be referred to as the control interface 242. The control signals 241 are used to control operation of the transmitter 130. The control signals 241 may also include status signals from the encryption engine 134 to the processor 120 via the side channel 240. Alternatively or additionally, in FIG. 2, the determination of whether a sink/external device (not shown in FIG. 2) supports the minimum level of encryption may be indicated in status signals transmitted via the side channel 240.

The side channel 240 is separate from and of lower speed than the data channel 122. In the HDMI example, the side channel 240 typically has an aggregate data rate of 100 Kbps—1 Mbps, while the data channel 122 has an aggregate data rate of 750 Mbps and often much more. The data channel 122 is typically at least 700 times higher data rate than the side channel 240, and may be 1,000 times higher data rate or even 10,000 times higher data rate. In another embodiment, the side channel 240 is an I2C bus. In yet another embodiment, the side channel 240 is a shared bus while the data channel 122 is a point-to-point link.

It might seem that the encryption control data 124 would more appropriately be transmitted over the side channel 240, rather than over the data channel 122. However, the side channel typically is lower speed than the data channel 122 and therefore more susceptible to tampering. This is especially true if the side channel 240 is a shared bus while the data channel 122 is a point-to-point link.

Consider the following scenario where the encryption process is compromised. The side channel 240 is a bus shared with another device (not shown in FIG. 2) connected thereto. In addition to the control signals 241 transmitted by the side channel 240, the processor 120 also transmits the encryption control data 124 over the side channel 240 instead of over the internal data channel 122. The transmitter 130 uses the level of encryption specified by the encryption control data 124 to apply encryption to the video data 132. If the other device having access to the side channel 240 modifies or tampers with the encryption control data 124, for example changing the level of encryption from HDCP 2.2 to no encryption, the transmitter 130 will be misinformed. In that situation, the transmitter 130 will not encrypt the video data and consequently will transmit it without encryption. This results in unencrypted video data being transmitted outside of the video processing device, when it should be transmitted using HDCP 2.2. This is a security problem.

This inadvertent situation is mitigated in FIGS. 1 and 2 because the encryption control data 124 is not transmitted via the side channel 240. Instead, it is transmitted only via the internal data channel 122, which is not shared with or otherwise accessible by other devices in the video processing device. Additionally, the internal data channel 122 has a much higher transmission speed than the side channel 240, making it more difficult to be tampered with. Thus, using only the internal data channel 122 to transmit the encryption control data 124 improves encryption security.

Now refer to FIG. 3, a flow diagram illustrating status reporting regarding whether a sink/external device supports a minimum encryption level. The transmitter 130 receives 310 a minimum encryption level specified by the encryption control data to be applied by the encryption engine 234. The transmitter 130 queries 320 the sink/external device's encryption capability and determines 330 whether the sink/external device supports the minimum encryption level, respectively. If the sink/external device supports the minimum encryption level, a “Pass” status signal is transmitted 340 via the side channel 240 to the processor 120. The transmitter 130 also encrypts and transmits 350 the video data. If the sink/external device does not support the minimum encryption level, a “Fail” status signal is transmitted 360 via the side channel 240 to the processor 120. The transmitter 130 may choose to nevertheless encrypt and transmit 370 the video data, even though the sink/external device will not be able to decrypt the video. It may do this because the determination 330 of the sink/external device's capability may be wrong. Alternately, the transmitter 130 could not transmit 370 the video data. In either case, the video data is not compromised because it is not transmitted using less than the minimum required encryption level.

FIG. 4 is a state diagram illustrating locking of encryption level. This can be used to maintain overall security in a situation where the encryption control data 124 could be sent via either the more secure internal data channel 122 or via the less secure side channel 240. Two states of the encryption engine 134 are shown in FIG. 4: the lock state 410 and the unlock state 420. In the lock state 410, the encryption engine will follow only encryption control data received via the internal data channel 122 and will ignore encryption control data received via the side channel 240. Thus, the encryption level applied by the encryption engine 134 cannot be changed by the side channel 240. In other words, it can only be changed by the internal data channel 122. In the unlock state 420, the encryption engine will follow encryption control data received via either channel 122, 240 and therefore the encryption level can be changed by either the side channel 240 or by the internal data channel 122.

In addition to the encryption level, the encryption control data can also include a lock instruction 430/440 or an unlock instruction 450/460. These instructions are used to change the lock state of the encryption engine 134. Specifically, in the lock state 410, a lock instruction 430 keeps the encryption engine in the lock state 410. An unlock instruction 450 places the encryption engine in the unlock state 420, but note that an unlock instruction 450 from the side channel 240 will be ignored since the encryption engine is in the lock state. Similarly, in the unlock state 420, an unlock instruction 460 keeps the encryption engine in the unlock state 420, while a lock instruction 440 places the encryption engine to the lock state 410. In addition, the encryption engine 134 may be configured to automatically change 470 from the lock state 410 to the unlock state 420 if no lock/unlock instruction to place or keep the encryption engine in the lock state is received during a predetermined timeout period. In various embodiments, this timeout period is 200 ms, for example.

FIG. 5 is a block diagram of one example implementation. In this example, the processor and the transmitter are implemented as separate integrated circuits, or chips. The internal data channel 122 between the processor and the transmitter includes conductive leads 522 coupling pins 521 of the data transmit interface 121 to pins 531 of the data receive interface 131.

Similarly, pins 536 of the data output interface 136 are coupled to an external connection 538 to transmit encrypted video data via the external data channel 138. In the example of FIG. 5, the external connection is made through a mechanical connector 538, for example and HDMI or MHL connector. In an alternative example (not shown), the external connection is made through a wireless connection. Examples of the wireless connection include, but are not limited to, Wi-Fi, Bluetooth, and wireless data connections for mobile phones and tablets, such as various technologies under 3G and LTE.

FIG. 6 is a block diagram of another example implementation. In this example, the encryption engine 134 is implemented in a third chip that is separate from the processor and rest of the transmitter. When the transmitter (chip 2) receives the unencrypted video data and encryption control data from the data receive interface 131, it transmits the unencrypted video data and encryption control data to the encryption engine 134 (chip 3) for encryption. After encryption, the encrypted video data is transmitted from the encryption engine 134 back to the transmitter, which then transmits the encrypted video data to the external data channel 138 via the data transmit interface 136.

Although the detailed description contains many specifics, these should not be construed as limiting the scope of the disclosure but merely as illustrating different examples and aspects of the disclosure. It should be appreciated that the scope of the disclosure includes other embodiments not discussed in detail above. Various other modifications, changes and variations which will be apparent to those skilled in the art may be made in the arrangement, operation and details of the method and apparatus of the present disclosure without departing from the spirit and scope of the disclosure as defined in the appended claims. Therefore, the scope of the disclosure should be determined by the appended claims and their legal equivalents. 

What is claimed is:
 1. A transmitter for encrypting and transmitting video data, comprising: a data receive interface configured to receive unencrypted video data and encryption control data via pin(s) from a first data channel; an encryption engine coupled to the data receive interface, the encryption engine encrypting the unencrypted video data in accordance with the encryption control data; and a data output interface coupled to the encryption engine, the data output interface configured to transmit the encrypted video data via pin(s) to a second data channel.
 2. The transmitter of claim 1, wherein the encryption control data specifies a level of encryption applied by the encryption engine.
 3. The transmitter of claim 2, wherein the encryption engine comprises a register that stores the level of encryption to be applied by the encryption engine.
 4. The transmitter of claim 1, wherein the encryption control data specifies whether or not to apply encryption.
 5. The transmitter of claim 1, wherein: the data output interface is configured to transmit the encrypted video data to an external device via the second data channel; the encryption control data specifies a minimum level of encryption applied by the encryption engine; the transmitter determines whether the external device supports the minimum level of encryption; and if the external device does not support the minimum level of encryption, the transmitter is configured to not transmit data over the second data channel.
 6. The transmitter of claim 1, further comprising: a control interface configured to receive control signals via pin(s) from a side channel that is separate from and lower speed than the data channel, the control signals controlling operation of the transmitter.
 7. The transmitter of claim 6, wherein: the encryption control data includes lock/unlock instructions that place the encryption engine into a lock state or into an unlock state; in a lock state, a level of encryption applied by the encryption engine cannot be changed by data received via the side channel; and in an unlock state, the level of encryption applied by the encryption engine can be changed by data received via the side channel.
 8. The transmitter of claim 7, wherein the encryption engine automatically changes from a lock state to an unlock state, if no lock/unlock instruction to place or keep the encryption engine in the lock state is received during a predetermined timeout period.
 9. The transmitter of claim 6, wherein the data channel is at least 1000 times higher data rate than the side channel.
 10. The transmitter of claim 6, wherein the side channel is a shared bus and the data channel is a point-to-point link.
 11. The transmitter of claim 6, wherein the control interface is further configured to transmit status signals via the pin(s) to the side channel.
 12. The transmitter of claim 11, wherein: the data output interface transmits the encrypted video data to an external device via the second data channel; the encryption control data specifies a level of encryption applied by the encryption engine; the transmitter determines whether the external device supports the specified level of encryption; and the status signal transmitted via the side channel indicates whether the external device supports the specified level of encryption.
 13. The transmitter of claim 1, wherein the data output interface transmits data in compliance with the HDMI, MHL or DisplayPort standards, and the encryption engine is an HDCP encryption engine.
 14. A processor, comprising a data transmit interface configured to transmit unencrypted video data and encryption control data via pin(s) to a first data channel, the encryption control data determining encryption to be applied to the unencrypted video data.
 15. A device comprising: a processor comprising a data transmit interface; a transmitter comprising a data receive interface; a first data channel coupled on one end via pin(s) to the data transmit interface, and on the other end via pin(s) to the data receive interface, the first data channel transporting unencrypted video data and encryption control data from the processor to the transmitter; the transmitter further comprising: an encryption engine coupled to the data receive interface, the encryption engine encrypting the unencrypted video data in accordance with the encryption control data; and a data output interface coupled to the encryption engine, the data output interface configured to transmit the encrypted video data via an external connection to a second data channel.
 16. The device of claim 15, wherein the processor and transmitter are implemented as separate integrated circuits, and the first data channel includes conducting leads connecting pins of the separate integrated circuits.
 17. The device of claim 15, wherein, in the transmitter, the encryption engine is implemented as an integrated circuit that does not contain the data receive interface or the data output interface.
 18. The device of claim 15, wherein the external connection is made through mechanical connectors.
 19. The device of claim 15, wherein the external connection is made through a wireless connection.
 20. The device of claim 15, wherein the data output interface transmits the encrypted video data via the second data channel to an external display device. 